Ticketing systems on a distributed ledger

ABSTRACT

A blockchain system for providing ticketing within a blockchain network of participating electronic devices includes an electronic gaming machine (EGM) configured to participate in the blockchain network. The EGM a memory storing a local blockchain and a system blockchain. The EGM also includes at least one processor configured to execute instructions which, when executed, cause the at least one processor to identify a first ticket creation blockchain transaction in the local blockchain from a ticket creation device of the first plurality of electronic gaming devices, the first ticket creation blockchain transaction including at least a ticket value and a ticket identifier (ID), create a system ticket creation blockchain transaction including at least the ticket value and the ticket ID, and broadcast the system ticket creation blockchain transaction to the system blockchain.

CROSS-REFERENCE TO RELATED APPLICATION

This patent application claims the benefit priority of U.S. ProvisionalPatent Application Ser. No. 62/855,429, filed May 31, 2019, entitledTICKETING SYSTEMS ON A DISTRIBUTED LEDGER, the entire contents anddisclosure of which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

The field of disclosure relates generally to electronic gaming, and moreparticularly to electronic gaming systems and methods for providingcoinless ticketing using blockchain technology.

BACKGROUND

Electronic gaming machines (EGMs), or gaming devices, provide a varietyof wagering games such as, for example, and without limitation, slotgames, video poker games, video blackjack games, roulette games, videobingo games, keno games, and other types of games that are frequentlyoffered at casinos and other locations. Play on EGMs typically involvesa player establishing a credit balance by inserting or otherwisesubmitting money and placing a monetary wager (deducted from the creditbalance) on one or more outcomes of an instance, or play, of a primarygame, sometimes referred to as a base game. In many games, a player mayqualify for secondary games or bonus rounds by attaining a certainwinning combination or other triggering event in the base game.Secondary games provide an opportunity to win additional game instances,credits, awards, jackpots, progressives, etc. Awards from any winningoutcomes are typically added back to the credit balance and can beprovided to the player via a printed “ticket” upon completion of agaming session or when the player wants to “cash out.”

“Slot” type games are often displayed to the player in the form ofvarious symbols arrayed in a row-by-column grid or matrix. Specificmatching combinations of symbols along predetermined paths (or paylines)through the matrix indicate the outcome of the game. The displaytypically highlights winning combinations/outcomes for readyidentification by the player. Matching combinations and theircorresponding awards are usually shown in a “pay-table” which isavailable to the player for reference. Often, the player may varyhis/her wager to include differing numbers of paylines and/or the amountbet on each line. By varying the wager, the player may sometimes alterthe frequency or number of winning combinations, frequency or number ofsecondary games, and/or the amount awarded.

Many modern EGMs provide coinless ticketing (“ticket-in/ticket-out,” or“TITO”), a print-based technology that allows players to exchange valuewith EGMs via printed ticket rather than via coin currency. SuchTITO-based EGMs typically include a bill validator, a ticket reader, anda ticket printer. During game play, a player may insert cash into thebill validator to establish a credit at the EGM. The player uses theircredit to place wagers during game play (e.g., for slot gaming, virtualpoker, keno, and such). Upon conclusion of their gaming session, whenthe player “cashes out,” the EGM uses the ticket printer to print aticket for the player. The ticket is a voucher embodying the player'sunused credit from their play session. The player may then redeem thatvoucher at either a cashier (e.g., for cash) or at another TITO-basedEGM (e.g., for credit). When the player chooses to play at another EGM,the player inserts the ticket into the ticket reader. The EGM collectsthe ticket and establishes the appropriate credit on the EGM for gameplay.

Coinless ticketing systems have provided improvements in the electronicgaming industry. However, such conventional ticketing systems rely upona client/server architecture that presents technical challengesincluding, for example, system reliability (e.g., outages, uptime,system maintenance, single point of failure) and security (e.g.,hacking, auditing, regulatory compliance). It would be beneficial tohave a ticketing system that mitigated many of the technical problems ofconventional ticketing systems.

BRIEF SUMMARY

In one aspect, a blockchain system for providing ticketing within ablockchain network of participating electronic devices is provided. Theblockchain system includes an electronic gaming machine configured toparticipate in the blockchain network. The electronic gaming machineincludes a memory storing a local blockchain and a system blockchain.The local blockchain supports a first plurality of electronic gamingdevices of the blockchain network. The system blockchain supports asecond plurality of electronic gaming devices of the blockchain network.The electronic gaming machine also includes at least one processorconfigured to execute instructions. When executed, the instructionscause the at least one processor to identify a first ticket creationblockchain transaction in the local blockchain from a ticket creationdevice of the first plurality of electronic gaming devices. The firstticket creation blockchain transaction includes at least a ticket valueand a ticket identifier (ID). The instructions also cause the at leastone processor to create a system ticket creation blockchain transactionincluding at least the ticket value and the ticket ID. The instructionsfurther cause the at least one processor to broadcast the system ticketcreation blockchain transaction to the system blockchain.

In another aspect, a computer-implemented method for providing ticketingwithin a blockchain network of participating electronic devices sharinga blockchain is provided. The method is performed by an electronicgaming machine participating as a node in the blockchain network. Theblockchain is a distributed ledger tracking redeemable tickets. Themethod includes receiving an initiation of a cash-out event by a playerof the electronic gaming machine. The method also includes identifying acredit balance at the electronic gaming machine. The method furtherincludes generating a ticket identifier for a redeemable ticket. Themethod also includes creating a first blockchain transaction includingat least (1) a ticket value equal to the credit balance, (2) the ticketidentifier, and (3) a transaction type identifying the first blockchaintransaction as a ticket creation transaction within the blockchain. Themethod further includes transmitting the first blockchain transaction toone or more nodes of the blockchain network for addition to theblockchain.

In yet another aspect, a computer-implemented method for providingticketing within a peer-to-peer blockchain network of participatingelectronic devices sharing a blockchain is provided. The method isperformed by an electronic gaming machine participating as a node in thepeer-to-peer blockchain network. The blockchain is a distributed ledgertracking redeemable tickets. The method includes receiving, at a ticketreader of the electronic gaming machine, a physical ticket forredemption, the physical ticket including a ticket identifier. Themethod also includes identifying the ticket identifier from the physicalticket. The method further includes searching the blockchain for (1) aticket creation transaction associated with the ticket identifier andfor (2) an existing ticket redemption transaction associated with theticket identifier, the ticket creation transaction including a ticketvalue. When the ticket creation transaction associated with the ticketidentifier is located by the search and when the existing ticketredemption transaction is not located by the search, the method includesestablishing a credit at the electronic gaming machine for an amountequal to the ticket value identified in the ticket creation transactionwithin the blockchain, creating a ticket redemption transactionincluding the ticket identifier, and transmitting the ticket redemptiontransaction to one or more nodes of the peer-to-peer blockchain networkfor addition to the blockchain.

In still another aspect, a system of electronic devices participating ina peer-to-peer blockchain network sharing a blockchain is provided. Theblockchain is a distributed ledger tracking redeemable tickets. Thesystem includes a first participating device. The first participatingdevice is configured to receive a ticket generation request, identify aticket value and source of funds to apply to the ticket generationrequest, generate a ticket identifier for a redeemable ticket, create afirst blockchain transaction including at least (1) the ticket value,(2) the ticket identifier, and (3) a transaction type identifying thefirst blockchain transaction as a ticket creation transaction within theblockchain, transmit the first blockchain transaction to one or morenodes of the peer-to-peer blockchain network for addition to theblockchain, and print a physical ticket at a ticket printer of the firstparticipating device, the physical ticket including the ticketidentifier. The system also includes a second participating device. Thesecond participating device is configured to receive, at a ticket readerof the second participating device, the physical ticket for redemption,read the ticket identifier from the physical ticket, search theblockchain for (1) a ticket creation transaction associated with theticket identifier and for (2) an existing ticket redemption transactionassociated with the ticket identifier, the ticket creation transactionincluding a ticket value, determine that the physical ticket is validand active based on the search, redeem the ticket value at the secondparticipating device, create a ticket redemption transaction includingthe ticket identifier, and transmit the ticket redemption transaction toone or more nodes of the peer-to-peer blockchain network for addition tothe blockchain.

BRIEF DESCRIPTION OF THE DRAWINGS

An example embodiment of the subject matter disclosed will now bedescribed with reference to the accompanying drawings.

FIG. 1 is a diagram of exemplary EGMs networked with variousgaming-related servers.

FIG. 2 is a block diagram of an exemplary EGM.

FIG. 3 is a networked environment of a ticketing blockchain system inwhich various devices provide ticketing using a distributed ledger(e.g., a blockchain).

FIG. 4 is a networked environment of a ticketing blockchain system inwhich EGMs provide ticketing using one or more blockchains.

FIG. 5 is a data flow diagram illustrating various blockchain operationsperformed within the ticketing blockchain system.

FIG. 6A illustrates an example method for creating a ticket using theticketing blockchain system and the P2P network shown in FIG. 3.

FIG. 6B illustrates an example method for redeeming the ticket createdin FIG. 6A using the ticketing blockchain system and the P2P network.

DETAILED DESCRIPTION

A ticketing blockchain system is described herein that may be used todecentralize aspects of coinless ticketing transaction management,allowing EGMs to provide coinless TITO using blockchain technology.Decentralized ledger technology (e.g., blockchain) may be used toprovide a distributed ledger amongst participating nodes in a blockchainnetwork (e.g., a peer-to-peer network) that may provide aspects ofdecentralization, tracking, immutability, security, and transparency fortransaction data added to the ledger. Conventional TITO systems using acentralized architecture typically rely upon a server (e.g., a TITOserver) to centrally manage TITO ticket operations (e.g., ticketcreation, management, and redemption). Such centralization can besubject to certain exposures, such as server downtime or single point offailure, data integrity risks (e.g., tampering, corruption, hacks), orthe like. Aspects of blockchain technology and associated distributedarchitecture can provide a technological solution to many of theseproblems of centralized architectures.

In an example embodiment, aspects of blockchain technology are employedby the ticketing blockchain system to support ticketing for a group ofparticipating EGMs in a permissioned blockchain. The ticketingblockchain system establishes one or more blockchains that are used toconduct and manage ticketing transactions. Various trusted electronicdevices may participate in the ticketing blockchain system, such as EGMs(e.g., for creating tickets and redeeming tickets for credit at thegaming device), gaming tables or associated support devices (e.g., forissuing or redeeming tickets for chips at the gaming tables), tellernodes (e.g., kiosks and cashier devices for redeeming tickets for cash),and administrative nodes (e.g., for audit, accounting, and varioussupport functionality). When a player initiates a cash out operation atan EGM, the EGM prints a ticket with the credit balance of the playerand also creates a “ticket-out” transaction within the ticketingblockchain system that memorializes the ticket-out transaction for thatticket into the blockchain (e.g., credit value, ticket identifier,ticket account, source device identifier, and perhaps other accountingand auditing data). When the player redeems the ticket at a transactingnode (e.g., at an EGM, a teller node, or the like), the transacting nodereads the ticket information from the ticket and searches the blockchainto determine whether the ticket is authentic and valid. If the search ofthe blockchain identifies the previously-entered “ticket-out”transaction within the blockchain and verifies that the ticket has notyet been redeemed (e.g., no existing “ticket-in” transaction in theblockchain or in other pending transactions), then the ticket isverified as valid and active. Once verified, the transacting nodecreates a “ticket-in” transaction within the ticketing blockchain systemthat memorializes the ticket-in transaction, thereby identifying theticket as redeemed. The transacting node provides the value of theticket to the player (e.g., as a credit for the player at thetransacting device, confirming eligibility for a cash payment to theplayer at a kiosk, table, or cashier, or the like). As such, theticket-in transaction being added to the blockchain serves as notice toall other participating nodes that the once-active ticket is no longeractive, as having been previous redeemed in full.

In some embodiments, the ticketing blockchain system provides a tieredarchitecture of blockchains. The tiered architecture groups EGMs intoEGM clusters. Each EGM cluster includes several EGMs that may bephysically in proximity to each other (e.g., two to twelve EGMs). EachEGM cluster shares a cluster blockchain isolated to that cluster, witheach EGM in the cluster participating in the cluster blockchain as aticketing blockchain node. There may be several EGM clusters at a givenproperty or across several properties.

In addition, one node of each EGM cluster is designated as a “leadernode” for that cluster. Each of the leader nodes of the various EGMclusters participates in a “system blockchain” in which dozens orhundreds of EGMs may participate. The leader nodes for each cluster actas transaction replicators between the cluster blockchains and thesystem blockchain. As nodes add ticket deposit transactions into thecluster blockchain (e.g., as tickets are created) or add ticketwithdrawal transactions into the cluster blockchain (e.g., as ticketsare redeemed), the leader node for that cluster inspects the clusterblockchain for new transactions. Any transactions newly added to thecluster blockchain are then replicated by the leader node out into thesystem blockchain, thereby causing the cluster deposits and withdrawalsto be reflected in the overall system-level blockchain. Similarly, theleader node also inspects the system blockchain for any transactionsnewly added by other system-level nodes and replicates those deposits(or withdrawals) into the cluster blockchain.

In example embodiments, the ticketing blockchain system is comprised oftrusted nodes in a permissioned blockchain network. The ticketingblockchain provides no tokenization or rewards for mining, as there isno need to incentivize participation for the work contributed by thenodes. Further, the processing and energy consumption demands to nodeson the blockchain can be reduced by replacing the proof of work (“PoW”)processing with other consensus mechanisms that dictate which node willadd the next block to the blockchain, such as proof of stake (“PoS”),tangle, swirlds, delegated proof of stake, proof of selection, one ormore delegated block generators, or the like.

FIG. 1 illustrates several different models of EGMs which may benetworked to various gaming related servers. Shown is a system 100 in agaming environment including one or more server computers 102 (e.g.,slot servers of a casino) that are in communication, via acommunications network, with one or more gaming devices 104A-104X (EGMs,slots, video poker, bingo machines, etc.) that can implement one or moreaspects of the present disclosure. The gaming devices 104A-104X mayalternatively be portable and/or remote gaming devices such as, but notlimited to, a smart phone, a tablet, a laptop, or a game console,although such devices may require specialized software and/or hardwareto comply with regulatory requirements regarding devices used forwagering or games of chance in which monetary awards are provided.

Communication between the gaming devices 104A-104X and the servercomputers 102, and among the gaming devices 104A-104X, may be direct orindirect, such as over the Internet through a website maintained by acomputer on a remote server or over an online data network includingcommercial online service providers, Internet service providers, privatenetworks, and the like. In other embodiments, the gaming devices104A-104X may communicate with one another and/or the server computers102 over RF, cable TV, satellite links and the like.

In some embodiments, server computers 102 may not be necessary and/orpreferred. For example, in one or more embodiments, a stand-alone gamingdevice such as gaming device 104A, gaming device 104B or any of theother gaming devices 104C-104X can implement one or more aspects of thepresent disclosure. However, it is typical to find multiple EGMsconnected to networks implemented with one or more of the differentserver computers 102 described herein.

The server computers 102 may include a central determination gamingsystem server 106, a ticket-in-ticket-out (TITO) system server 108, aplayer tracking system server 110, a progressive system server 112,and/or a casino management system server 114. Gaming devices 104A-104Xmay include features to enable operation of any or all servers for useby the player and/or operator (e.g., the casino, resort, gamingestablishment, tavern, pub, etc.). For example, game outcomes may begenerated on a central determination gaming system server 106 and thentransmitted over the network to any of a group of remote terminals orremote gaming devices 104A-104X that utilize the game outcomes anddisplay the results to the players.

Gaming device 104A is often of a cabinet construction which may bealigned in rows or banks of similar devices for placement and operationon a casino floor. The gaming device 104A often includes a main door 154which provides access to the interior of the cabinet. Gaming device 104Atypically includes a button area or button deck 120 accessible by aplayer that is configured with input switches or buttons 122, an accesschannel for a bill validator 124, and/or an access channel for aticket-out printer 126.

In FIG. 1, gaming device 104A is shown as a Relm XLTM model gamingdevice manufactured by Aristocrat® Technologies, Inc. As shown, gamingdevice 104A is a reel machine having a gaming display area 118comprising a number (typically 3 or 5) of mechanical reels 130 withvarious symbols displayed on them. The reels 130 are independently spunand stopped to show a set of symbols within the gaming display area 118which may be used to determine an outcome to the game.

In many configurations, the gaming machine 104A may have a main display128 (e.g., video display monitor) mounted to, or above, the gamingdisplay area 118. The main display 128 can be a high-resolution LCD,plasma, LED, or OLED panel which may be flat or curved as shown, acathode ray tube, or other conventional electronically controlled videomonitor.

In some embodiments, the bill validator 124 may also function as a“ticket-in” reader that allows the player to use a casino issued creditticket to load credits onto the gaming device 104A (e.g., in a cashlessticket (“TITO”) system). In such cashless embodiments, the gaming device104A may also include a “ticket-out” printer 126 for outputting a creditticket when a “cash out” button is pressed. Cashless TITO systems areused to generate and track unique bar-codes or other indicators printedon tickets to allow players to avoid the use of bills and coins byloading credits using a ticket reader and cashing out credits using aticket-out printer 126 on the gaming device 104A. The gaming machine104A can have hardware meters for purposes including ensuring regulatorycompliance and monitoring the player credit balance. In addition, therecan be additional meters that record the total amount of money wageredon the gaming machine, total amount of money deposited, total amount ofmoney withdrawn, total amount of winnings on gaming device 104A.

In some embodiments, a player tracking card reader 144, a transceiverfor wireless communication with a player's smartphone, a keypad 146,and/or an illuminated display 148 for reading, receiving, entering,and/or displaying player tracking information is provided in EGM 104A.In such embodiments, a game controller within the gaming device 104A cancommunicate with the player tracking system server 110 to send andreceive player tracking information.

Gaming device 104A may also include a bonus topper wheel 134. When bonusplay is triggered (e.g., by a player achieving a particular outcome orset of outcomes in the primary game), bonus topper wheel 134 isoperative to spin and stop with indicator arrow 136 indicating theoutcome of the bonus game. Bonus topper wheel 134 is typically used toplay a bonus game, but it could also be incorporated into play of thebase or primary game.

A candle 138 may be mounted on the top of gaming device 104A and may beactivated by a player (e.g., using a switch or one of buttons 122) toindicate to operations staff that gaming device 104A has experienced amalfunction or the player requires service. The candle 138 is also oftenused to indicate a jackpot has been won and to alert staff that a handpayout of an award may be needed.

There may also be one or more information panels 152 which may be aback-lit, silkscreened glass panel with lettering to indicate generalgame information including, for example, a game denomination (e.g.,$0.25 or $1), pay lines, pay tables, and/or various game relatedgraphics. In some embodiments, the information panel(s) 152 may beimplemented as an additional video display.

Gaming devices 104A have traditionally also included a handle 132typically mounted to the side of main cabinet 116 which may be used toinitiate game play.

Many or all the above described components can be controlled bycircuitry (e.g., a gaming controller) housed inside the main cabinet 116of the gaming device 104A, the details of which are shown in FIG. 2.

Note that not all gaming devices suitable for implementing embodimentsof the present disclosure necessarily include top wheels, top boxes,information panels, cashless ticket systems, and/or player trackingsystems. Further, some suitable gaming devices have only a single gamedisplay that includes only a mechanical set of reels and/or a videodisplay, while others are designed for bar counters or table tops andhave displays that face upwards.

An alternative example gaming device 104B illustrated in FIG. 1 is theArc™ model gaming device manufactured by Aristocrat® Technologies, Inc.Note that where possible, reference numerals identifying similarfeatures of the gaming device 104A embodiment are also identified in thegaming device 104B embodiment using the same reference numbers. Gamingdevice 104B does not include physical reels and instead shows game playfunctions on main display 128. An optional topper screen 140 may be usedas a secondary game display for bonus play, to show game features orattraction activities while a game is not in play, or any otherinformation or media desired by the game designer or operator. In someembodiments, topper screen 140 may also or alternatively be used todisplay progressive jackpot prizes available to a player during play ofgaming device 104B.

Example gaming device 104B includes a main cabinet 116 including a maindoor 154 which opens to provide access to the interior of the gamingdevice 104B. The main or service door 154 is typically used by servicepersonnel to refill the ticket-out printer 126 and collect bills andtickets inserted into the bill validator 124. The main or service door154 may also be accessed to reset the machine, verify and/or upgrade thesoftware, and for general maintenance operations.

Another example gaming device 104C shown is the Helix™ model gamingdevice manufactured by Aristocrat® Technologies, Inc. Gaming device 104Cincludes a main display 128A that is in a landscape orientation.Although not illustrated by the front view provided, the landscapedisplay 128A may have a curvature radius from top to bottom, oralternatively from side to side. In some embodiments, display 128A is aflat panel display. Main display 128A is typically used for primary gameplay while secondary display 128B is typically used for bonus game play,to show game features or attraction activities while the game is not inplay or any other information or media desired by the game designer oroperator. In some embodiments, example gaming device 104C may alsoinclude speakers 142 to output various audio such as game sound,background music, etc.

Many different types of games, including mechanical slot games, videoslot games, video poker, video black jack, video pachinko, keno, bingo,and lottery, may be provided with or implemented within the depictedgaming devices 104A-104C and other similar gaming devices. Each gamingdevice may also be operable to provide many different games. Games maybe differentiated according to themes, sounds, graphics, type of game(e.g., slot game vs. card game vs. game with aspects of skill),denomination, number of paylines, maximum jackpot, progressive ornon-progressive, bonus games, and may be deployed for operation in Class2 or Class 3, etc.

In the example embodiment, the TITO system server 108 participates as anadministrative node in a ticketing blockchain (not depicted in FIG. 1).The TITO system server 108 includes blockchain software that allows forthe server 108 to perform blockchain functionality such as, for example,receiving and inspecting the blockchain, broadcasting transactions intothe blockchain, and creating blocks for the blockchain (e.g., mining).Various ticketing blockchain functionality is described in greaterdetail below.

FIG. 2 is a block diagram depicting exemplary internal electroniccomponents of a gaming device 200 connected to various external systems.All or parts of the example gaming device 200 shown could be used toimplement any one of the example gaming devices 104A-X depicted inFIG. 1. The games available for play on the gaming device 200 arecontrolled by a game controller 202 that includes one or more processors204 and a game that may be stored as game software or a program 206 in amemory 208 coupled to the processor 204. The memory 208 may include oneor more mass storage devices or media that are housed within gamingdevice 200. Within the mass storage devices and/or memory 208, one ormore databases 210 may be provided for use by the program 206. A randomnumber generator (RNG) 212 that can be implemented in hardware and/orsoftware is typically used to generate random numbers that are used inthe operation of game play to ensure that game play outcomes are randomand meet regulations for a game of chance.

Alternatively, a game instance (i.e. a play or round of the game) may begenerated on a remote gaming device such as a central determinationgaming system server 106 (not shown in FIG. 2 but see FIG. 1). The gameinstance is communicated to gaming device 200 via the network 214 andthen displayed on gaming device 200. Gaming device 200 may execute gamesoftware, such as but not limited to video streaming software thatallows the game to be displayed on gaming device 200. When a game isstored on gaming device 200, it may be loaded from a memory 208 (e.g.,from a read only memory (ROM)) or from the central determination gamingsystem server 106 to memory 208. The memory 208 may include RAM, ROM oranother form of storage media that stores instructions for execution bythe processor 204. Note that embodiments of the present disclosurerepresent an improvement in the art of EGM software and provide atechnological improvement in the field of EGM technology in that the EGMblockchain technology described herein utilizes aspects of blockchaintechnology to provide a decentralized ticketing amongst multiple EGMs ina secure fashion and that eliminates the need for some traditionalhardware elements.

The gaming device 200 may include a topper display 216 or another formof a top box (e.g., a topper wheel, a topper screen, etc.) which sitsabove cabinet 218. The cabinet 218 or topper display 216 may also housea number of other components which may be used to add features to a gamebeing played on gaming device 200, including speakers 220, a ticketprinter 222 which prints bar-coded tickets or other media or mechanismsfor storing or indicating a player's credit value, a ticket reader 224which reads bar-coded tickets or other media or mechanisms for storingor indicating a player's credit value, and a player tracking interface232. The player tracking interface 232 may include a keypad 226 forentering information, a player tracking display 228 for displayinginformation (e.g., an illuminated or video display), a card reader 230for receiving data and/or communicating information to and from media ora device such as a smart phone enabling player tracking. Ticket printer222 may be used to print tickets for a TITO system server 108. Thegaming device 200 may further include a bill validator 234, player-inputbuttons 236 for player input, cabinet security sensors 238 to detectunauthorized opening of the cabinet 218, a primary game display 240, anda secondary game display 242, each coupled to and operable under thecontrol of game controller 202.

Gaming device 200 may be connected over network 214 to player trackingsystem server 110. Player tracking system server 110 may be, forexample, an OASIS® system manufactured by Aristocrat® Technologies, Inc.Player tracking system server 110 is used to track play (e.g. amountwagered, games played, time of play and/or other quantitative orqualitative measures) for individual players so that an operator mayreward players in a loyalty program. The player may use the playertracking interface 232 to access his/her account information, activatefree play, and/or request various information. Player tracking orloyalty programs seek to reward players for their play and help buildbrand loyalty to the gaming establishment. The rewards typicallycorrespond to the player's level of patronage (e.g., to the player'splaying frequency and/or total amount of game plays at a given casino).Player tracking rewards may be complimentary and/or discounted meals,lodging, entertainment and/or additional play. Player trackinginformation may be combined with other information that is now readilyobtainable by a casino management system.

Gaming devices, such as gaming devices 104A-104X, 200, are highlyregulated to ensure fairness and, in many cases, gaming devices104A-104X, 200 are operable to award monetary awards (e.g., typicallydispensed in the form of a redeemable voucher). Therefore, to satisfysecurity and regulatory requirements in a gaming environment, hardwareand software architectures are implemented in gaming devices 104A-104X,200 that differ significantly from those of general-purpose computers.Adapting general purpose computers to function as gaming devices 200 isnot simple or straightforward because of: 1) the regulatory requirementsfor gaming devices 200, 2) the harsh environment in which gaming devices200 operate, 3) security requirements, 4) fault tolerance requirements,and 5) the requirement for additional special purpose componentryenabling functionality of an EGM. These differences require substantialengineering effort with respect to game design implementation, hardwarecomponents and software.

When a player wishes to play the gaming device 200, he/she can insertcash or a ticket voucher through a coin acceptor (not shown) or billvalidator 234 to establish a credit balance on the gamine machine. Thecredit balance is used by the player to place wagers on instances of thegame and to receive credit awards based on the outcome of winninginstances. The credit balance is decreased by the amount of each wagerand increased upon a win. The player can add additional credits to thebalance at any time. The player may also optionally insert a loyaltyclub card into the card reader 230. During the game, the player viewsthe game outcome on one or more of the primary game display 240 andsecondary game display 242. Other game and prize information may also bedisplayed.

For each game instance, a player may make selections, which may affectplay of the game. For example, the player may vary the total amountwagered by selecting the amount bet per line and the number of linesplayed. In many games, the player is asked to initiate or select optionsduring course of game play (such as spinning a wheel to begin a bonusround or select various items during a feature game). The player maymake these selections using the player-input buttons 236, the primarygame display 240 which may be a touch screen, or using some other devicewhich enables a player to input information into the gaming device 200.

During certain game events, the gaming device 200 may display visual andauditory effects that can be perceived by the player. These effects addto the excitement of a game, which makes a player more likely to enjoythe playing experience. Auditory effects include various sounds that areprojected by the speakers 220. Visual effects include flashing lights,strobing lights or other patterns displayed from lights on the gamingdevice 200 or from lights behind the information panel 152 (FIG. 1).

When the player is done, he/she cashes out the credit balance (typicallyby pressing a cash out button to receive a ticket from the ticketprinter 222). The ticket may be “cashed-in” for money or inserted intoanother machine to establish a credit balance for play.

In the example embodiment, the gaming device 200 participates in one ormore blockchains that support TITO ticketing. Ticketing operations maybe memorialized as blockchain transactions, thereby decentralizingticketing amongst participating nodes (e.g., EGMs, table games, tellernodes, admin nodes). When the gaming device 200 inserts cash in the billvalidator 234 or a ticket into the ticket reader 224, the gaming device200 may create and broadcast a coin-in transaction or a ticket-intransaction, respectively, into the blockchain while establishing acredit on the gaming device 200 (e.g., to an EGM account). When theplayer cashes out, the gaming device 200 not only prints a ticketrepresenting the player's credit balance, but also creates andbroadcasts a ticket-out transaction into the blockchain to create theticket.

FIG. 3 is a networked environment of a ticketing blockchain system 300in which various devices provide ticketing using a distributed ledger(e.g., blockchain) 310. In the example embodiment, the system 300includes a blockchain network 302 (e.g., a peer-to-peer (“P2P”) network)in which various devices participate in a permissioned blockchain 310that is used for issuing and redeeming TITO tickets (e.g., within agaming environment). Participating devices may include gaming devices104, kiosks (or cashier devices) 330, TITO system server 108, and gamingtables 332 (e.g., table games which support TITO ticketing at tables),each of which may be involved in the issuing, redeeming, or accountingof TITO tickets 304. For example, gaming devices 104, kiosks 330, ortable games 332 may be configured to issue TITO tickets (or just“ticket”) 304 to players 306, typically by printing a slip of paper thatthe player 306 can carry around and redeem at various gaming venues,kiosks/cashiers 330, or the like. Redeeming devices can accept thetickets 304, typically using an optical scanner to read data from theticket 304, such as a unique ticket identifier (“ticket ID”), a value,or other authentication information, each of which may be embodied in anoptical label that can visually embody data, such as a QR code or abarcode. The ticket 304 represents a cashless method of embodying cashvalue that can be of convenience to players 306 during their gamingexperiences, allowing the player 306 to minimize the use of cash duringgame play. While the participating devices are coupled in networkedcommunication through underlying networking technology not shown ordescribed here for purposes of brevity, it should be understood thatblockchain network 302 shown in FIG. 3 represents devices participatingin a peer-to-peer relationship with other devices permissioned toparticipate in the blockchain 310, but may also include aspects ofcentralized communication (e.g., between gaming devices 104 and TITOsystem server 108). Blockchain network 302 may include any underlyingnetworking technologies, hardware, or protocols sufficient to enable thesystems and methods described herein.

In the example embodiment, the participating devices (also referred toherein as “nodes”) of the network 302 perform ticketing transactions(e.g., ticket creations, ticket redemptions) and track ticketing datathrough the blockchain 310. One example ticketing transaction performedin the blockchain 310 is a “ticket-out” transaction. When a new ticketis to be created at a participating node (e.g., during a “cash-out”operation at a gaming device 104), that device is responsible foraccepting value from the player 306, printing the ticket 304, and fortransmitting a ticket-out transaction into the blockchain 310 (i.e.,into the blockchain network 302) for addition as a “blockchaintransaction” to the blockchain 310. The ticket-out transactionmemorializes the new ticket and various information within theblockchain 310, which may subsequently be used to during ticketredemption.

Another example ticket transaction performed in the blockchain 310 is a“ticket-in” transaction. When a ticket is presented for redemption at aparticipating node (e.g., during a “ticket-in” operation at a gamingdevice 104, kiosk/cashier 330, or table 332), that redeeming device isresponsible for scanning information from the ticket, validating throughthe blockchain 310 that the ticket is valid and unredeemed, transmittinga “ticket-in” transaction into the blockchain 310, and providing orotherwise authorizing the transfer of the ticket value to the player306. The ticket-in transaction memorializes the redemption of thatticket within the blockchain 310, thereby changing the status of theticket to redeemed and thus prohibiting other devices from redeeming theticket a second time.

The blockchain 310 includes a linked list of blocks 312. Each block 312,in the example embodiment, includes a previous hash 314, a timestamp316, and one or more blockchain transaction records (also referred toherein as “block transaction data,” “TX DATA”, or simply transactions orrecords) 318. As is known in the art, blockchain technology uses aspectsof encryption and digital signatures to create a distributed, immutableledger (e.g., the blockchain 310). The network 302 uses a cryptographichash function (e.g., SHA-256, Merkle Trees, Keccak/SHA-3, or the like)to generate and memorialize a hash of the previous block as the previoushash 314. The block transaction data 318 includes a record for eachtransaction added to a particular block 312. The blocks 312 may containother components not expressly called out here for purposes of brevity.As is known in the art, all nodes in the network 302 execute ablockchain client that allows participation in the network 302 andmaintains a copy of the blockchain 310 and may also include pendingtransactions received from other peer nodes prior to memorializationinto a new block 312. Further, each node in the network 302 maintains aunique identity in the network 302 and may generate and use a uniquepublic/private key pair, maintaining the private key locally andpublishing the public key to other nodes in the network (e.g., forvalidating transactions added to the blockchain 310). It should beunderstood that the present disclosure uses many aspects of blockchaintechnology (e.g., Blockchain 1.0, Blockchain 2.0 technologies) and,particularly, for permissioned blockchains and smart contracts, that arenot expressly described herein for purposes of brevity.

In some embodiments, the ticketing blockchain system 300 is comprised oftrusted nodes in a permissioned blockchain network (e.g., network 302)that provides no tokenization or rewards for mining, as there is no needto incentivize participation for the work contributed by the nodes.Further, the processing and energy consumption demands to nodes on theblockchain can be reduced by replacing the proof of work (“PoW”)processing with other consensus mechanisms that dictate which node willadd the next block to the blockchain, such as proof of stake (“PoS”),tangle, swirlds, delegated proof of stake, proof of selection, one ormore delegated block generators, or the like. As such, any of theparticipating devices may be eligible to consolidate transactions andadd blocks 312 to the blockchain 310 and can avoid the processingoverhead of typical proof of work consensus protocols.

In the example embodiment, certain types of blockchain transactions 318may include various data fields that allow the blockchain 310 tomemorialize various information that facilitates both the creation,tracking, and redemption of tickets 304, as well as supportingaccounting, auditing, and regulatory compliance of the ticketingblockchain system 300. For example, ticket-in and ticket-out typetransactions include a ticket value indicating a redemption value forthe ticket (e.g., currency value, credit value, or the like). At thetime of a ticket-out event, the issuing device determines a ticket valueof the ticket (e.g., based on a current credit total of the player 306at a gaming device 104, based on an amount paid by the player 306 at akiosk/cashier device 330).

Each such transaction also includes a unique ticket ID for the ticket304. The ticket ID is a unique ID for each ticket generated and used bythe ticketing blockchain system 300. In some embodiments, the issuingdevice generates the unique ticket ID when creating the ticket (e.g., byconcatenating a unique machine identifier of the issuing device togetherwith a unique ticket string or index locally generated and tracked bythe device, with a timestamp, or the like). In other embodiments, acentral server, such as the TITO system server 108, may provide uniqueticket IDs to the participating nodes within the network 302 duringticket creation. In some embodiments, the TITO system server 108 mayprovide a validation code for the ticket 304 that is recorded in theblockchain 310, and that validation code may be used as the ticket ID oras a part of the ticket ID. The ticket ID is used by the ticketingblockchain system 300, in some cases, as an account number for theticket within the blockchain 310.

Once the issuing device identifies the ticket data, the issuing deviceprints the ticket 304 at a local ticket printer (e.g., ticket printer222), including ticket ID and ticket value, optical image, and the like.The issuing device also broadcasts a ticket-out transaction to theblockchain 310 (e.g., as a blockchain transaction 318 into the network302). The ticket-out transaction includes a transaction type (e.g., acode identifying this blockchain transaction 318 as a ticket-outtransaction, ticket creation transaction, or the like), the uniqueticket ID, and the ticket value. In some embodiments, the ticket-outtransaction may include a device ID of the issuing device, a ticketissuance timestamp, or a player ID (e.g., a unique ID identifying theplayer 306 to which the ticket is issued). Having been broadcast intothe network 302, this ticket-out transaction will eventually be bundledtogether with other transactions and added to the blockchain 310 by amining node or other duly elected node, subsequently updating theblockchain 310 with the new block throughout the network 302. Theticket-out transaction effectively acts to publish the validity of a newticket into the network 302.

When the player 306 presents the ticket 304 for redemption (e.g., at agaming device 104, kiosk/cashier device 330, table game 332, or thelike), the redeeming device scans the ticket 304 to read the embodiedinformation on the ticket 304 (e.g., the ticket ID). The redeemingdevice uses the ticket ID to determine whether the ticket is valid(e.g., properly created) and active (e.g., not yet redeemed or otherwisecancelled) by scanning the blockchain 310 and other pending transactionsfor transactions 318 identifying that particular ticket ID. Otherpending transactions refers to transactions 318 that have been submittedfor addition to the blockchain 310 but, due to timing considerations,have not yet been memorialized in a new block 312 of the blockchain 310.If the ticket 304 is verified as both valid and still active, then theredeeming device determines a redemption value for the ticket 304 basedon the ticket-out transaction in the blockchain 310 and provides thatredemption value to the player 306 (e.g., via credit on a gaming device104, via chips at a table game 332, via alerting a cashier to presentcash to the player 306 at a cage, via cash payout or balance transfer toa player account at a kiosk, or the like). Further, the redeeming devicebroadcasts a ticket-in type transaction to the blockchain 310 (e.g., asa blockchain transaction 318 into the network 302). The ticket-intransaction includes a transaction type (e.g., a code identifying thisblockchain transaction 318 as a ticket-in transaction, ticket redemptiontransaction, or the like) and the unique ticket ID. In some embodiments,the ticket-in transaction may include a device ID of the redeemingdevice, a ticket redemption timestamp, a player ID of the redeemingplayer (e.g., a unique ID identifying the player 306 to which the ticketis redeemed), or a redemption value. Having been broadcast into thenetwork 302, this ticket-in transaction will eventually be bundledtogether with other transactions and added to the blockchain 310 by amining node or other duly elected node, subsequently updating theblockchain 310 with the new block throughout the network 302. Theticket-in transaction effectively acts to publish the redemption of anexisting ticket, thereby causing the ticket to become inactive after oneredemption.

In some embodiments, the ticketing blockchain system 300 may facilitateother blockchain uses for the blockchain 310 and participating devices.In other words, the blockchain 310 may support other types of blockchaintransactions unrelated to ticketing. For example, the ticketingblockchain system 400 may track coin-in events within the blockchain(s)412, 422. During a coin-in event, a gaming device 104 may generate acoin-in type blockchain transaction 318 to include a dollar valueaccepted from a bill validator 234, a unique device ID of the gamingdevice 104, and a timestamp. In some embodiments, the EGM 410B may alsogenerate a unique coin-in ID for each coin-in event similar to theunique ticket ID. In such embodiments, the coin-in transaction 318 maybe treated as a source of value for a later ticket-out transaction atthat gaming device 104.

In normal operation, each transaction 318 propagates throughout thenetwork 302 and is thus available to any of the participating devices,eventually appearing in their local copy of the blockchain 310. However,in some situations, one or more participating devices may becomeseparated, segmented, or otherwise disconnected from some or all of theticketing blockchain system 300. For example, presume a gaming device104 becomes isolated from the network 302 at a point in time. In such asituation, if that gaming device 104 generates and prints a new ticket304 with a value of $50.00, the corresponding broadcast of theticket-out transaction 318 to the broader network 302 will fail (e.g.,not be received by any of the other participating devices), and thuswill not get promptly added to the blockchain 310. As such, if theplayer 306 takes the ticket 304 to another participating device, thatredemption device will not be able to locate and verify the ticket-outtransaction 318 associated with that ticket 304 (referred to herein asan “unidentified ticket” scenario).

In some embodiments, when an unidentified ticket is submitted forredemption to another participating device, that device may refuse tohonor the ticket 304, may hold or return the ticket 304 to the player306, or may alert staff to investigate the issue.

In the example embodiment, validation codes are included with each newticket transaction, and may be used during unidentified ticketscenarios. Validation codes serve as a secret signature (e.g., generatedvia RNG) that may be associated with a particular ticket and used forauthentication of the ticket. In some embodiments, validation codes maybe generated by the TITO ticket server 108. In other embodiments,validation codes may be generated by the issuing devices. In someembodiments, a pool of pre-generated validation codes for tickets may becreated and assigned to issuing devices. The pre-generated validationcodes for all nodes in the blockchain 310 are stored in the blockchain310 and, as such, all nodes have knowledge of all of the pre-generatedvalidation codes. During a segmentation scenario (e.g., if a nodetemporarily loses network communication with other nodes in the network302, or a cluster blockchain temporarily loses communication with thesystem blockchain), the segmented device may utilize one of thepre-generated validation codes during new ticket generation. Because ofthe segmentation, the locally-generated transaction may not be able tobe fully transmitted to the other parts of the network 302. However,since all nodes have knowledge of the pre-generated validation code, theother nodes can still validate at least the authenticity of the code,though not able to verify the credit value printed on the ticket 304versus the credit value within the associated blockchain transaction(e.g., the ticket-out transaction 318 for that ticket 304). In someembodiments, the ticketing blockchain system 400 may be configured toredeem such segmented tickets (e.g., tickets not appearing in theirversion of the blockchain 310 but having an authentic validation code)if certain segmented ticket validation criteria are met. For example,the operator may be willing to accept risk for tickets under a certainpre-determined threshold (e.g., less than $100 or less than $500), orfor a certain period of time (e.g., less than 10 minutes old, less than30 minutes old).

FIG. 4 is a networked environment of a ticketing blockchain system 400in which EGMs provide ticketing using one or more blockchains 412, 422.In some embodiments, aspects of the ticketing blockchain system 400 maybe similar to the ticketing blockchain system 300 of FIG. 3, and theblockchains 412, 422 may be similar to the blockchain 310 shown in FIG.3. In the example embodiment, the ticketing blockchain system 400includes a set of EGMs 410A-N (collectively, EGMs 410) logically groupedtogether as an EGM cluster 414. EGMs 410 may be grouped into EGMclusters 414 based on, for example, physical proximity to each other(e.g., a bank of EGMs, a room of EGMs at a property, all of the EGMs ata particular property), network connectivity (e.g., by subnet or IPrange, by shared connectivity to a particular network device), or by alogical grouping (e.g., a set of EGMs participating in a particularprogressive, a new set of EGMs recently installed at a property). Eachof the EGMs 410 may be similar to the gaming devices 104 shown in FIG. 1or the gaming device 200 shown in FIG. 2. The EGMs 410 arenetwork-connected to a local area network (LAN) 402 (e.g., anEthernet/IP network). While not individually numbered, several EGMclusters similar to EGM cluster 414 are illustrated in FIG. 4. And whilenot individually numbered, each of those EGM clusters similarly containsone or more EGMs similar to the EGMs 410 of EGM cluster 414.

In the example embodiment, each EGM 410 participates as a node in acluster blockchain 412. The cluster blockchain 412 is a blockchain thatis restricted to only the EGMs 410 within that cluster 414. Each EGM 410of the cluster 414 executes a blockchain software service (notseparately shown) that allows the EGM 410 to participate in blockchains(e.g., as participating nodes of the cluster blockchain 412 and/or thesystem blockchain 422). Each of the EGMs 410 within the cluster 414shares the cluster blockchain 412, may inspect the cluster blockchain412, may broadcast transactions into the cluster blockchain 412 (e.g.,as tickets are generated or redeemed), and may bundle transactions intoblocks and add blocks to the cluster blockchain 412, validate blocks ofthe cluster blockchain 412, or otherwise participate in the clusterblockchain 412. As such, the EGMs 410A-410N are the set of participatingnodes in the cluster blockchain 412. In some embodiments, EGMs 410 areconfigured (e.g., by a technician) with a cluster identifier associatedwith a particular EGM cluster 414 and each EGM joins the cluster (e.g.,during reboot, start-up of blockchain services, or such). A transactionmay be added to the cluster blockchain 412 documenting the registrationevents.

Each EGM cluster 414, in the example embodiment, also designates one ofthe EGMs 410 as a “leader node” 416 for that EGM cluster 414. In theexample shown in FIG. 4, EGM_1 410A is currently designated as theleader node 416 for that cluster 414. Similarly, each of the otherclusters also has a leader node 416 designated. The remaining nodes ofthe cluster 414 are considered subordinate nodes 418. Each leader node416, in addition to participating in the cluster blockchain 412 fortheir own cluster 414, additionally participates in the systemblockchain 422. The system blockchain 422 is configured to journaltickets, and in some cases cash deposits, across all EGM clusters 414,as well as perhaps other non-clustered EGMs. In some embodiments, thesystem blockchain 422 may also include remote EGMs 432 (e.g., fromstand-alone EGMs or similarly-clustered EGMs) across a wide area network(WAN) 430. The collection of EGMs or other devices (e.g., TITO systemserver 108) participating in the system blockchain 422 are referred toherein as system nodes 420. As such, leader nodes 416 participate inboth their local cluster blockchain 412 and the system blockchain 422.In some embodiments, any EGM 410 of a cluster 414 may be designated asthe leader node 416, and the designation of the leader node 416 may bedynamically determined or transferred from one EGM 410 to another EGM410 within the cluster 414 at any time (e.g., if the current leader node416 goes offline or is otherwise unable to participate as the leadernode 416). In some embodiments, the designation of leader node isprovided to an EGM 410 of the cluster 414 that is otherwise idle (e.g.,not currently being operated by a player).

During operation, EGMs 410 generate coin-in or ticket-in transactions(e.g., during coin-in or ticket-in events) or ticket-out transactions(e.g., as tickets are printed) that are broadcast to the other EGMs 410within the cluster 414. One of the EGMs 410 successfully bundles one ormore transactions into a new block and adds the new block to the clusterblockchain 412. As such, the transactions are added to the ledger withinthe cluster blockchain 412, and may also increase or decrease ledgertotals for accounts associated with tickets or EGMs. Each of the EGMs410 in the cluster 414 also receive a copy of the new block, validatethe new block, and determine, from the blockchain, what tickets arelegitimate and unredeemed.

Additionally, other EGMs are informed of the new transactions generatedby EGMs 410 of the EGM cluster 414. More specifically, the leader node416 of the cluster 414 replicates cluster-level transactions (e.g.,transactions made by cluster EGMs 410) out into the system blockchain422 as “outbound replicated transactions.” The leader node 416 isconfigured to monitor their local cluster blockchain 412 for any newcluster-level transactions. Each newly-detected cluster-leveltransaction is copied by the leader node 416 and broadcast as a newtransaction out into the system blockchain 422 (e.g., to all of thesystem nodes 420). One of the system nodes 420 bundles those newtransactions, perhaps with other transactions 509, and successfully addsa new block to the system blockchain 422, thereby updating thesystem-level ledger with updated information on tickets.

The leader nodes 416 also replicate new transactions into their EGMcluster 414 as “inbound replicated transactions.” The leader node 416 isconfigured to monitor the system blockchain 422 for any new system-leveltransactions. Each newly-detected system-level transaction is copied bythe leader node 416 and broadcast as a new transaction into the clusterblockchain 412 (e.g., to all of the cluster EGMs 410). One of thecluster EGMs 410 bundles those new transactions, perhaps with othertransactions 509, and successfully adds a new block to the clusterblockchain 412, thereby updating the cluster-level ledger with updateddeposits from other EGMs outside of the cluster 414. Each cluster EGM410 may then determine, from the cluster blockchain 412, which ticketsare legitimate and unredeemed.

In some embodiments, EGMs 410 or system nodes 420 contend to bundletransactions and add new blocks to the cluster blockchain 412 or thesystem blockchain 422, respectively, based on techniques known in theart (e.g., by proof of work). In other words, each EGM 410 in the EGMcluster 414 may act as a miner node, and each leader node 416 or othersystem node 420 in the system blockchain 422 may act as a miner node. Inthe example embodiment, at the cluster level, one of the EGMs 410 ineach EGM cluster 414 is designated the blocking node for the cluster414, and that one node collects and bundles all cluster-leveltransactions into the cluster blockchain 412. For example, the adminnode 424 may be designated the blocking node for the blockchain 422(e.g., for nodes 420), the leader nodes 416 may be designated theblocking nodes for their respective clusters 414, or the TITO systemserver 108 may be designated the blocking node for the blockchain 310.In some embodiments, the EGMs 410 contend to be the blocking node forthe cluster 414 (e.g., randomly, by a single proof of work contest, bycontending for control of a shared resource (semaphore), or such). Insome embodiments, the system-level nodes may similarly designate asystem-level blocking node for the system blockchain 422 by any of theabove-described methods.

In some embodiments, an admin node 424 participates in the systemblockchain 422. The admin node 424 may broadcast transactions into thesystem blockchain 422, access the blockchain 422, or otherwiseparticipate as a node in the system blockchain 422. In some embodiments,the TITO system server 108 may be the admin node 424. The admin node 424may perform management operations associated with ticketing operationsbeing provided by the ticketing blockchain system 400. For example, theadmin node 424 may generate validation codes (e.g., secret signatures)for tickets generated by the ticketing blockchain system 400, validatetickets, or perform administrative functions.

In the example embodiment, the blockchains 412, 422 are configured toadd a new block on a periodic, regular basis. For example, theblockchains 412, 422 may be configured to add a new block to theirrespective blockchains 412, 422 every 0.1 seconds or every 0.5 seconds(e.g., if there are any new transactions to be added). The blockchains412, 422 may define or otherwise include a blocking interval settingthat may be used by the blocking nodes to determine when and howfrequently to bundle transactions and generate a new block. In someembodiments, each of the blocking nodes may share a heartbeat to timewhen new blocks are added into each cluster blockchain 412 and when newblocks are added into the system blockchain 422. The heartbeat inconjunction with carefully timed blocking between the cluster level andthe system level may allow the ticketing blockchain system 400 tominimize latency for propagation of transactions out from the clusterblockchains 412 into the system blockchain 422 and subsequently backdown into the other cluster blockchains 412. Shorter blocking intervalsgenerally increase propagation time for transactions through theblockchain 412 but may incur greater resource costs (e.g., moreprocessing time, more total blocks added to the blockchains 412, 422over time). The frequency interval of the leader nodes 416 may beseparately configurable for outbound replication timing going from thecluster blockchain 412 out into the system blockchain 422 or for inboundreplication timing going from the system blockchain 422 into the clusterblockchain 412.

In some embodiments, individual (e.g., un-clustered) EGMs mayparticipate in the system blockchain 422. In some embodiments, theblockchains 412, 422 may additionally include data not associated withticketing. For example, the EGMs may use the blockchains 412, 422 tomemorialize audit data, accounting data, player data, game play data,administer progressive jackpots, or other data generated by or otherwiseassociated with electronic game play at the EGMs. In some embodiments,the ticketing blockchain system 400 may implement components or modulesof blockchain technology such as is associated with Hyperledger Fabrictechnology. In some embodiments, the ticketing blockchain system 400 mayinclude a third tier of sub-clustered EGMs (e.g., with one EGM acting asleader node between, for example, EGM cluster 414 and a sub-cluster ofEGMs (not shown)).

FIG. 5 is a data flow diagram 500 illustrating various blockchainoperations performed within the ticketing blockchain system 400. In theexample embodiment, diagram 500 illustrates an outbound replicationprocess and an inbound replication process for coin-in and TITOtransactions. For the outbound replication process, various EGMs 410within the EGM cluster 414 generate coin-in/ticket-in transactions 508or ticket-out transactions 510 during game play. For example, during thecoin-in/ticket-in transaction 508, a player 502 may insert cash or aticket 506 into a bill validator 504 at EGM_2 410B. During theticket-out transaction 510, the EGM 410B may print the ticket 506 from aticket printer (not separately shown in FIG. 5). Each transaction 508,510 represents a transaction that is broadcast to the EGM cluster 414for addition to the cluster blockchain 412. Periodically, the nodes ofthe cluster 414 (e.g., the blockchain services executing on the EGMs410) collect multiple transactions from other nodes of the cluster 414,bundle those transactions into a new cluster block 512, and may contendwith other nodes of the cluster 414 to add the new cluster block 512 tothe cluster blockchain 412. In the example shown here, EGM_2 410B hasbeen tasked to add new cluster block 512 to the cluster blockchain 412(depicted here as arrow 514).

The leader node 416 of EGM cluster 414, EGM_1 (“leader node”) 410A,inspects the cluster blockchain 412 looking for any new transactionadded to the blockchain 412. In the example embodiment, the leader node410A identifies the new cluster block 516 (depicted here as arrow 518)and extracts the new transaction 508, 510 from the block 516. The leadernode 410A then broadcasts the transaction 508, 510 out to the systemnodes 420 as a new transaction for addition into the system blockchain422 (depicted here as arrow 520). One of the nodes within the systemnodes 420 collects the new transaction 508, 510, and perhaps othertransactions 509 broadcast within the system nodes 420, bundles thosetransactions 508, 510 into a new system block (“new sys block A”) 522,and may contend with other nodes of the system nodes 420 to add the newsys block A 522 to the system blockchain 422. In this example, one ofthe system nodes 420 (not depicted) has been tasked to add the newsystem block A 522 to the system blockchain 422 (depicted here as arrow524). As such, new transactions being generated from within the EGMcluster 414 are both memorialized within the cluster blockchain 412, andare also replicated out to the system blockchain 422, thereby completingthe outbound replication process.

For the inbound replication process, the leader node 410A of EGM cluster414 identifies that a new system block (“new sys block B”) 528 has beenadded to the system blockchain 422 (depicted here as arrow 530). The newsystem block 528 includes new transactions 526 (e.g., one or moretransactions not yet processed by the leader node 410A). The leader node410A extracts the new transactions 526 from the block 528 and broadcastseach of those new transactions 526 into the EGM cluster 414 (e.g., toall of the cluster EGMs 410) (depicted here as arrow 532). While notseparately depicted here, these new transactions 526 may subsequently beadded to the cluster blockchain 412 similar to how the transactions 508,510 were added as described above. As such, new transactions beinggenerated from outside the EGM cluster 414 are both memorialized withinthe system blockchain 422, and is also replicated into the clusterblockchain 412, thereby completing the inbound replication process.

Transactions 508, 510 include various data fields that allow theblockchains 412, 422 to memorialize various information that facilitatesboth the tracking and redemption of tickets 506 as well as supportingaccounting, auditing, and regulatory compliance of the ticketingblockchain system 400. In the example embodiment, ticket-in andticket-out type transactions include a credit value indicating aredemption value for the ticket. At the time of a ticket-out event, theEGM 410B prints the ticket 506, broadcasts the ticket-out transaction tothe EGM cluster 414 (e.g., as described above), and sets the creditvalue of the ticket to be equal to the current credit total of theplayer 502 at the EGM. The ticket 506 may have the credit value printedon the ticket 506 during a ticket-out transaction. During a ticket-intransaction, the credit value identified within the blockchain 412, 422for that ticket is the redemption value used when redeeming that ticket(e.g., credit amount given on another EGM, dollar value given at acashier's window or redemption kiosk).

Ticket-in and ticket-out type transactions, in the example embodiment,also include a ticket identifier (“ID”). The ticket ID is a unique IDfor each ticket generated by the ticketing blockchain system 400. Insome embodiments, the EGM 410B generates the unique ticket ID byconcatenating a unique machine identifier associated with the EGM 410Btogether with a unique ticket string locally generated and tracked bythe EGM 410B (e.g., a subsequent number in a sequence, a timestamp). Insome embodiments, the ticket ID includes a ticket validation codeprovided and tracked by the TITO system (e.g., the TITO system server108). The ticket ID is used by the ticketing blockchain system 400, insome cases, as an account number for the ticket within the blockchains412, 422. When the new ticket 506 is created, the EGM 410B generates thenew ticket ID and adds that ticket ID to the ticket-out transaction 510.When the ticket 506 is later redeemed (e.g., at another EGM, kiosk, orcashier's device in the ticketing blockchain system 400), the ticket-outtransaction 510 is located within the blockchain 412, 422 by theredeeming device based on the ticket ID provided on the ticket 506.Further, the ticket ID is then added to the ticket-in transaction 508 bythe redeeming device. In some embodiments, the blockchains 412, 422 mayinclude one ticket-out transaction with a positive credit to the ticketID and one ticket-in transaction with a negative credit from the ticketID.

In some embodiments, transactions 508, 510 may include a source deviceID of the EGM creating the ticket 506 (e.g., in a ticket-out transaction510) or of the redeeming device (e.g., in a ticket-in transaction 508).Transactions 508, 510 may also include a timestamp of the transaction508, 510. In some embodiments, transactions 508, 510 may include atransaction type ID (e.g., coin-in, ticket-in, ticket-out).

In some embodiments, the ticketing blockchain system 400 may trackcoin-in events within the blockchain(s) 412, 422. For example, during acoin-in event, the EGM 410B may generate the coin-in transaction 508 toinclude a dollar value accepted from the bill validator 504, the EGM ID,and a timestamp. In some embodiments, the EGM 410B may also generate aunique coin-in ID for each coin-in event similar to the unique ticketID. In such embodiments, the coin-in transaction 508 may be treated as asource of value for a later ticket-out transaction at that EGM 410B.

In normal operation, each transaction 508, 510 propagates throughout theblockchains 412, 422 and is thus available to any of the participatingdevices (e.g., EGMs 410, system nodes 420, admin nodes 424, teller nodes426, remote EGMs 432, and so forth). However, in some situations, one ormore EGMs 410 may become separated, segmented, or otherwise disconnectedfrom some or all of the ticketing blockchain system 400. For example,presume EGM_2 410B becomes isolated from the EGM cluster 414 and thenetwork 402 at a point in time. In such a situation, if EGM_2 generatesand prints the new ticket 506 with a value of $50.00, the correspondingbroadcast of the ticket-out transaction 510 to the EGM cluster 414 willfail (e.g., not be received by any of the other EGMs 410), and thus willnot get promptly added to the blockchains 412, 422. As such, if theplayer 502 takes the ticket 506 to another EGM or other redemptiondevice, that redemption device will not be able to locate and verify theticket-out transaction 510 associated with the ticket 506 (referred toherein as an “unidentified ticket” scenario).

In some embodiments, when an unidentified ticket is submitted forredemption to another EGM, that EGM may refuse to honor the ticket 506,may hold or return the ticket 506 to the player 502, or may alert staffto investigate the issue.

In the example embodiment, validation codes are included with each newticket transaction. Validation codes serve as a secret signature (e.g.,generated via RNG) that may be associated with a particular ticket andused for authentication of the ticket. In some embodiments, validationcodes may be generated by the TITO ticket server 108. In otherembodiments, validation codes may be generated by the EGMs 410. In someembodiments, a pool of pre-generated validation codes for tickets may becreated and assigned to the EGM cluster 414 (e.g., administered by theleader node 416) or to individual EGMs 410. The pre-generated validationcodes for all nodes in the blockchains 412, 422 are stored in theblockchains 412, 422 and, as such, all nodes have knowledge of all ofthe pre-generated validation codes. During a segmentation scenario(e.g., if the EGM 410, leader node 416, or EGM cluster 414 isdisconnected from the broader system blockchain 422 or TITO ticketserver 108), the segmented EGM 410 may utilize one of the pre-generatedvalidation codes during new ticket generation. Because of thesegmentation, the locally-generated transaction may not be able to befully transmitted to the other parts of the blockchain 422. However,since all nodes have knowledge of the pre-generated validation code, theother nodes can still validate at least the authenticity of the code,though not able to verify the credit value printed on the ticket. Insome embodiments, the ticketing blockchain system 400 may be configuredto redeem such segmented tickets (e.g., tickets not appearing in thecurrent blockchain 412, 422 but having an authentic validation code) ifcertain segmented ticket validation criteria are met. For example, theoperator may be willing to accept risk for tickets under a certainpre-determined threshold (e.g., less than $100 or less than $500), orfor a certain period of time (e.g., less than 10 minutes old, less than30 minutes old).

FIG. 6A illustrates an example method 600 for creating a ticket 304using the ticketing blockchain system 300 and the network 302 shown inFIG. 3. In the example embodiment, the ticket creation process isdescribed as performed by a gaming device 104, 200 (e.g., as the“issuing device”) and in the context of a “cash-out” operation at thegaming device, where the player 306 holds a balance on the device andwishes to transfer that value to a ticket 304. However, it should beunderstood that this process can be performed by any participating nodein the network 302 that can print tickets 304 and participate in theblockchain 310, and that can accept value from the player 306 inresponse for embodying that value in the ticket 304.

At operation 610, in the example embodiment, the player 306 holds apositive balance at the gaming device 104 and initiates a cash-outoperation at the gaming device 104 (e.g., through pressing a mechanicalor virtual button on the gaming device 104). Upon detecting the cash-outplayer input, at operation 612, the gaming device 104 preparestransaction data for a new ticket-out (or “ticket creation”) blockchaintransaction 318 by generating a unique ticket ID for this ticket 304 atoperation 612 (e.g., concatenating a unique device ID with a currenttimestamp, or the like). The gaming device 104 also determines a ticketvalue for the ticket at operation 614 (e.g., based on a credit balanceon the gaming device 104). The gaming device 104 creates a ticket-outblockchain transaction 318 having the ticket ID and ticket value, andoptionally other data fields, and transmits that ticket-out transaction318 to the network 302 (e.g., broadcasting to neighbor nodes, or thelike) at operation 616. The gaming device 104 reduces the credit balanceon the gaming device 104 to zero and prints a physical TITO ticket(e.g., the ticket 304) which can be taken by the player 306.

In the example embodiment, the new ticket-out transaction 318 propagatesthrough the nodes of the network 302 and is eventually bundled togetherwith other transactions 318 and memorialized in a new block 312 that isadded to the blockchain 310 of all participating nodes at operation 620.It should be understood that the operations shown in broken line inFIGS. 6A and 6B are operations performed by a participating node in thenetwork 302 (e.g., a miner node or node that is otherwise tasked withcreating the next block 312 on the blockchain 310), and those operationsare not necessarily performed by the issuing or redeeming device.

FIG. 6B illustrates an example method 650 for redeeming the ticket 304created in FIG. 6A using the ticketing blockchain system 300 and thenetwork 302. In the example embodiment, the ticket redemption process isdescribed as performed by another gaming device 104, 200 (e.g., as the“redeeming device”) and in the context of a “ticket presentation”operation at the gaming device, where the player 306 inserts the ticket304 into the redeeming device (e.g., into ticket reader 224) in exchangefor a credit balance on the gaming device 104 (e.g., to begin a gameplay session). However, it should be understood that this process can beperformed by any participating node in the network 302 that can redeemtickets 304 and participate in the blockchain 310, and that can transfervalue to the player 306 in response to accepting the ticket 304.

At operation 660, in the example embodiment, the player 306 presents theticket 304 at the redeeming device (e.g., another gaming device 104). Atoperation 662, the gaming device 104 scans ticket information from theticket 304 (e.g., via optical scan) and determines the ticket ID forthat ticket 304, as well as optionally the ticket value or other dataembodied on the ticket. At operation 664, the gaming device 104 searchesthrough the blockchain 310 (e.g., the cluster blockchain 412) and anycurrent pending transactions not yet memorialized in the blockchain 310,using the ticket ID from the ticket 304 to identify any transactions forthat ticket ID. The ticket 304 is considered valid if the gaming device104 finds a ticket-out transaction for that ticket ID. If, at test 670,no ticket-out transaction for that ticket ID is found, then the gamingdevice 104 cancels redemption of the ticket 304, indicating the ticketas an unidentified and invalid ticket at operation 672. If a ticket-outtransaction is identified for the ticket 304, then the gaming device 104determines whether there is also a ticket-in (or “ticket redemption”)transaction for that ticket 304 already added to the blockchain network302 (e.g., added to the blockchain 310 or pending transaction). Theticket 304 is considered active if there is a ticket-out transactionwithout a corresponding ticket-in transaction, and inactive (or“redeemed”) if there is a ticket-out transaction with a correspondingticket-in transaction. If, at test 674, the gaming device 104 finds aticket-in transaction for the ticket 304, then the gaming device 104cancels redemption of the ticket 304, indicating the ticket as alreadyredeemed at operation 676.

Presuming the ticket 304 is valid and active, the gaming device 104creates a ticket-in blockchain transaction 318 having the ticket ID, andoptionally other data fields, and transmits that ticket-in transaction318 to the network 302 (e.g., broadcasting to neighbor nodes, or thelike) at operation 680. At operation 682, the gaming device 104increases the credit balance on the gaming device 104 by the ticketvalue (e.g., as memorialized in the ticket-out blockchain transaction318 identified by the search) and may retain the physical TITO ticket(e.g., the ticket 304) for later recovery and destruction by deviceoperators. The new ticket-in transaction 318 propagates through thenodes of the network 302 and is eventually bundled together with othertransactions 318 and memorialized in a new block 312 that is added tothe blockchain 310 of all participating nodes at operation 690. As such,the player 306 receives the ticket value one time, and that ticket issubsequently expired and invalid if a subsequent redemption attempt ofthe same ticket 304 is attempted.

In some embodiments, a virtual ticket may be issued (e.g., in additionto, or in lieu of, physically printing a ticket). For example, atoperation 618, a virtual ticket may be generated and transmitted to aknown player (e.g., a member of a loyalty program). The player 306 mayreceive, view, and use the virtual ticket via the player app installedon their personal mobile device. The gaming device 104 may transmit avirtual ticket to an account of the player 306 (e.g., managed by thecasino management system server 114 or the like), and that virtualticket may include any or all of the associated ticket information. Theplayer app is configured to display the virtual ticket such that theplayer 306 can present and scan the ticket (e.g., the opticalmachine-readable label) at an optical scanner of a gaming device 104,kiosk, or the like. In some embodiments, the player app may beconfigured to allow the player 306 to redeem the virtual ticket at aparticular device without scanning an optical code (e.g., afterwirelessly establishing a presence at the gaming device 104, gamingtable 332, kiosk, or the like). For example, the player app may beconfigured to wirelessly establish a presence at the particular device(e.g., gaming device 104, gaming table 332, kiosk, or the like), therebyidentifying a particular device as the redeeming device. When the player306 chooses to redeem the virtual ticket, the mobile device wirelesslycommunicates with the redeeming device or a backend support system(e.g., casino management system server 114, TITO system server 108, orthe like), identifying the ticket ID of the ticket to be redeemed andthe redeeming device. Upon verification of the ticket (e.g., as shown inFIG. 6B), the redeeming device provides the ticket value to the player306 (e.g., as credit balance on the gaming device 104) and marks thevirtual ticket as redeemed in the blockchain 310.

In some embodiments, the ticketing blockchain system 300 uses smartcontracts for redeeming the ticket 304. For example, the ticketingblockchain system 300 or another participating node may upload a ticketredemption smart contract (not separately depicted) into the blockchain310 that is configured to perform redemption operations. Morespecifically, a ticket 304 is created in the blockchain 310 (e.g., aftera ticket-out blockchain transaction 318 is created and added to theblockchain 310), as shown and described in FIG. 6A. Upon the playerpresenting the ticket at the redeeming device (e.g., at operation 660,662), the redeeming device may verify that the ticket 304 is valid andactive in the blockchain 310 (e.g., at operations 664-674). At operation680, the redeeming device transmits a ticket-in transaction to theblockchain 310 (e.g., at operation 680, 690), but the ticket-intransaction is not configured to transfer funds (e.g., does not performoperation 682). Rather, the ticket-in transaction is the recording of anevent for receiving the ticket, as well as a triggering condition forthe execution of the ticket redemption smart contract.

The ticket redemption smart contract is configured to trigger upondetection of any new ticket-in transactions. When a new ticket-intransaction is posted to the blockchain 310, the ticket redemption smartcontract executes. This smart contract reads the ticket ID from theticket-in transaction and may perform the searching and testingoperations (e.g., operations 664-676, but basing activity of the ticketon the lack of existence of a past redemption transaction for thatticket at test 674). Upon verification of a valid and active ticket 304,the smart contract creates and transmits a redemption transaction forthe ticket 304 and transmits that transaction into the blockchainnetwork 302 for addition to the blockchain 310. The redemptiontransaction includes the ticket ID, the ticket value, and the redeemingdevice ID. In some embodiments, the redemption transaction transfers theticket value from the ticket account to an account associated with theredeeming device. In some embodiments, the smart contract transmits anetwork message directly to the redeeming device verifying the validityof the ticket redemption, thus allowing the redeeming device to providethe ticket value to the player (e.g., at operation 682). In someembodiments, the redeeming device inspects blockchain transactions(e.g., in the blockchain 310, or pending transactions) looking for theredemption transaction associated with the ticket 304 before providingthe ticket value to the player.

A computer, controller, or server, such as those described herein,includes at least one processor or processing unit and a system memory.The computer, controller, or server typically has at least some form ofcomputer readable non-transitory media. As used herein, the terms“processor” and “computer” and related terms, e.g., “processing device”,“computing device”, and “controller” are not limited to just thoseintegrated circuits referred to in the art as a computer, but broadlyrefers to a microcontroller, a microcomputer, a programmable logiccontroller (PLC), an application specific integrated circuit, and otherprogrammable circuits “configured to” carry out programmableinstructions, and these terms are used interchangeably herein. In theembodiments described herein, memory may include, but is not limited to,a computer-readable medium or computer storage media, volatile andnonvolatile media, removable and non-removable media implemented in anymethod or technology for storage of information such as computerreadable instructions, data structures, program modules, or other data.Such memory includes a random access memory (RAM), computer storagemedia, communication media, and a computer-readable non-volatile medium,such as flash memory. Alternatively, a floppy disk, a compact disc-readonly memory (CD-ROM), a magneto-optical disk (MOD), and/or a digitalversatile disc (DVD) may also be used. Also, in the embodimentsdescribed herein, additional input channels may be, but are not limitedto, computer peripherals associated with an operator interface such as amouse and a keyboard. Alternatively, other computer peripherals may alsobe used that may include, for example, but not be limited to, a scanner.Furthermore, in the exemplary embodiment, additional output channels mayinclude, but not be limited to, an operator interface monitor.

As indicated above, the process may be embodied in computer software.The computer software could be supplied in a number of ways, for exampleon a tangible, non-transitory, computer readable storage medium, such ason any nonvolatile memory device (e.g. an EEPROM). Further, differentparts of the computer software can be executed by different devices,such as, for example, in a client-server relationship. Persons skilledin the art will appreciate that computer software provides a series ofinstructions executable by the processor.

While the invention has been described with respect to the figures, itwill be appreciated that many modifications and changes may be made bythose skilled in the art without departing from the spirit of theinvention. Any variation and derivation from the above description andfigures are included in the scope of the present invention as defined bythe claims.

What is claimed is:
 1. A blockchain system for providing ticketingwithin a blockchain network of participating electronic devices, theblockchain system comprising an electronic gaming machine configured toparticipate in the blockchain network, the electronic gaming machinecomprising: a memory storing a local blockchain and a system blockchain,the local blockchain supporting a first plurality of electronic gamingdevices of the blockchain network, the system blockchain supporting asecond plurality of electronic gaming devices of the blockchain network;and at least one processor configured to execute instructions which,when executed, cause the at least one processor to: identify a firstticket creation blockchain transaction generated in the local blockchainfrom a ticket creation device of the first plurality of electronicgaming devices, the first ticket creation blockchain transactionincluding at least a ticket value and a ticket identifier (ID); create asystem ticket creation blockchain transaction including at least theticket value and the ticket ID; and broadcast the system ticket creationblockchain transaction to the system blockchain.
 2. The blockchainsystem of claim 1, wherein the first ticket creation blockchaintransaction further includes a transaction type identifying the firstticket creation blockchain transaction as a ticket creation transaction.3. The blockchain system of claim 1, wherein the ticket ID identifies ablockchain account uniquely associated with the ticket ID, wherein thefirst ticket creation blockchain transaction is a blockchain transactionadding the ticket value to the blockchain account within the localblockchain, wherein broadcasting the system ticket creation blockchaintransaction to the system blockchain adds the ticket value to theblockchain account within the system blockchain.
 4. The blockchainsystem of claim 1, wherein identifying a first ticket creationblockchain transaction from a ticket creation device of the firstplurality of electronic gaming devices includes searching the localblockchain for ticket creation blockchain transactions not yetreplicated by the electronic gaming machine to the system blockchain. 5.The blockchain system of claim 1, wherein the electronic gaming machinecreates a new block including the first ticket creation blockchaintransaction that is accepted by the blockchain network for addition tothe local blockchain under a consensus protocol.
 6. The blockchainsystem of claim 5, wherein creating a new block includes: identifying aplurality of pending blockchain transactions for the local blockchainincluding the first ticket creation blockchain transaction; creating thenew block with the plurality of pending blockchain transactions; andbroadcasting the new block to the local blockchain for addition to thelocal blockchain.
 7. The blockchain system of claim 1, wherein theelectronic gaming machine is designated as a blocking node for the localblockchain.
 8. The blockchain system of claim 1, wherein theinstructions further cause the electronic gaming machine to: identify asystem ticket creation blockchain transaction from the systemblockchain, the system ticket creation blockchain transaction includingat least a second ticket value and a second ticket identifier (ID);create a local ticket creation blockchain transaction including at leastthe second ticket value and the second ticket ID; and add the localticket creation blockchain transaction to the local blockchain.
 9. Theblockchain system of claim 1, wherein the instructions further cause theelectronic gaming machine to: identify a ticket redemption blockchaintransaction that has not yet been replicated from one of the localblockchain and the system blockchain, the ticket redemption blockchaintransaction including at least a second ticket identifier (ID); create aticket redemption blockchain transaction, the ticket redemptionblockchain transaction including at least the ticket ID; and broadcastthe ticket redemption blockchain transaction to the other of the localblockchain and the system blockchain.
 10. The blockchain system of claim1, wherein the instructions further cause the electronic gaming machineto: receive an initiation of a cash-out event by a player of theelectronic gaming machine; identify a credit balance at the electronicgaming machine; and generate the ticket identifier for a redeemableticket, wherein identifying the first ticket creation blockchaintransaction from a ticket creation device of the first plurality ofelectronic gaming devices includes creating the first ticket creationblockchain transaction at the electronic gaming machine.
 11. Theblockchain system of claim 10 further comprising a ticket printer,wherein the instructions further cause the electronic gaming machine to:print the redeemable ticket at the ticket printer, the redeemable ticketincluding the ticket identifier; and reduce the credit balance at theelectronic gaming machine to zero after transmitting the firstblockchain transaction.
 12. The blockchain system of claim 11, whereinthe redeemable ticket further includes a validation code and a deviceidentifier of an issuing device, wherein the instructions further causethe at least one processor to: determine that the issuing device issegmented from the blockchain network; determine that the validationcode is a valid code assigned to the issuing device; and redeem theredeemable ticket for a ticket value printed on the redeemable ticketbased on validity of the validation code.
 13. The blockchain system ofclaim 10, wherein the instructions further cause the electronic gamingmachine to create a virtual redeemable ticket, the virtual redeemableticket including the ticket identifier, the virtual redeemable ticketbeing assigned to a player account of the player.
 14. The blockchainsystem of claim 1, wherein the instructions further cause the electronicgaming machine to: receive, at a ticket reader of the electronic gamingmachine, a physical ticket for redemption, the physical ticket includinga second ticket identifier; identify the second ticket identifier fromthe physical ticket; search one or more of the local blockchain and thesystem blockchain for (1) an existing ticket creation transactionassociated with the second ticket identifier within one or more of thesystem blockchain and the local blockchain and for (2) an existingticket redemption transaction associated with the second ticketidentifier in one or more of the system blockchain and the localblockchain, the existing ticket creation transaction including a ticketvalue; when the existing ticket creation transaction is located by thesearching and when the existing ticket redemption transaction is notlocated by the searching: establishing a credit at the electronic gamingmachine for an amount equal to the ticket value identified in theexisting ticket creation transaction; creating a ticket redemptiontransaction including the second ticket identifier; and transmitting theticket redemption transaction to one or more of the system blockchainand the local blockchain.
 15. The blockchain system of claim 14, whereinwhen either the existing ticket creation transaction associated with thesecond ticket identifier is not located by the searching or when theexisting ticket redemption transaction is located by the searching, theinstructions further cause the processor to reject ticket redemption.16. The blockchain system of claim 14, wherein the searching furtherincludes searching transactions within all accepted blocks within alocal copy of the one or more of the local blockchain and the systemblockchain and searching one or more pending transactions not yetmemorialized in an accepted block in the one or more of the localblockchain and the system blockchain.
 17. The blockchain system of claim1, wherein one or more of the local blockchain and the system blockchainfurther includes a smart contract configured to execute upon detectionof a new ticket redemption blockchain transaction, wherein execution ofthe smart contract includes: extracting a redemption ticket ID and aredemption ticket value from the new ticket redemption blockchaintransaction; validating that the redemption ticket ID is valid andactive within one or more of the local blockchain and the systemblockchain; and transmitting a message to a redeeming device identifiedwithin the new ticket redemption blockchain transaction authorizingpayment of the redemption ticket value.
 18. The blockchain system ofclaim 1, wherein the blockchain network is a peer-to-peer, permissionedblockchain of private nodes participating in one or more of the localblockchain and the system blockchain.
 19. The blockchain system of claim18, wherein the permissioned blockchain executes a consensus protocolnot including a proof of work protocol.
 20. The blockchain system ofclaim 1, wherein the first ticket creation blockchain transaction iscreated to further include one or more of a unique device identifier ofthe electronic gaming machine, a timestamp, and a player identifierassociated with the player.